home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Gold Collection
/
Software Vault - The Gold Collection (American Databankers) (1993).ISO
/
cdr37
/
faxdir.zip
/
FAXDIR.TBS
Wrap
Text File
|
1993-06-14
|
4KB
|
78 lines
Troubleshooting Guide - FaxDirect for ACT
1. Check the date of CAS_FAX.EXE. This is the file in the ACT
software that interacts with FAXDIR.EXE. It must be dated
5/20/92 or later. If it is not, the customer will need to
call Contact Software and update their files. They will need
to ask for the RETAIL version of ACT version 2.11a. If they
do not ask for the retail version, it is a good possibility
that Contact will send them the UPGRADE version which does not
update the CAS_FAX.EXE file.
2. Check the date of FAXDIR.EXE. This file should be dated
9/28/92 or later. These dates of Faxdirect will work with the
CAS_FAX.EXE file from ACT dated 5/20/92 or later.
3. Make sure the correct CLASS driver is installed. FaxDirect
will work with modems that support the CLASS1, CLASS2, or
SENDFAX standards. If the customer does not know what
standard their modem supports you can go into the setup of
FaxDirect by typing SETUPFD from the C:\FAXDIR dos prompt and
enter /DEBUG into the Optional Parameters: setting. Press F10
to save, and load FAXDIR. With the /Debug setting, Faxdirect
will issue the AT+FCLASS=? and the ATI3 commands to the modem
and return what is supported to the screen (eg. 0,1 would
indicate the modem supports CLASS1 specifications). Make sure
the /DEBUG is removed from SETUPFD, otherwise AT commands will
always be printed to the screen.
4. Make sure the correct COM port is selected in the setup (type
SETUPFD from the C:\FaxDirect directory).
5. FaxDirect currently does not ship with the PORTUTIL utility.
Check to the best of your ability to see if there might be any
hardware conflicts (eg COM1 and COM3 both share IRQ4 and COM2
and COM4 both share IRQ3).
6. Check to see if FAXSEND.EXE will send a document correctly
when FaxDirect is loaded (FAXSEND is shipped with FaxDirect
and interfaces with FaxDirect much like the CAS_FAX.EXE file
in ACT). You can have the customer send any ASCII text file
(autoexec.bat or config.sys would be fine since they are
already created). Type FAXSEND, then the ASCII filename
(C:\autoexec.bat), then a fax phone number. If everything is
set up correctly, it should report that the file has been
sent, then the modem should go off hook and dial the number
sending the fax correctly. If it does not send the fax
correctly, more troubleshooting is required.
7. If FAXSEND works correctly and ACT still will not send the
fax, have the customer go into the ACT software into FILE,-
FAX,- OPTIONS and make sure the FAX Board selection is set to
CAS COMPATIBLE FAX.
8. If the correct CLASS driver is installed and the modem is
having connection problems, try setting Highest Fax Speed in
SETUPFD.EXE from MAX to 9600 or even 4800 to narrow down the
problem.
9. Check to see if the customer has any other faxing software
that works correctly with their modem. If they do, and it
does work correctly, is it loaded at the same time as the
FaxDirect driver? The customer should not have any other
communications or faxing software loaded in RAM memory at the
same time as FaxDirect. If the other faxing software does not
work with the modem, most likely there is a hardware conflict
or a modem problem.
10. If the customer is experiencing random lockups, exception
errors, conflicts with other programs, EMM (expanded memory
manager) messages, you can try setting EMS usage to Do Not Use
in SETUPFD.EXE. Make sure FAXDIRECT is NOT loaded HIGH.
11. Have the customer try booting computer 'Vanilla' (free from
any software programs that stay resident in memory after they
are loaded) to see if there might be a conflict with the
FaxDirect driver which loads memory resident.
12. FaxDirect is not supported under OS/2 or Windows.